docs: add tentative bi-weekly community meetings schedule #198
Conversation
✅ Deploy Preview for vllm-semantic-router ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
👥 vLLM Semantic Team NotificationThe following members have been identified for the changed files in this PR and have been automatically assigned: 📁
|
wangchen615
force-pushed
the
add-community-meetings
branch
from
a1e6f49 to
fab4040
Compare
|
By the way, can we create a Google Calendar? This way everyone can easily subscribe and receive reminders automatically. |
|
@tao12345666333 Zoom will create a calendar ics file. We can import to Google calendar. And we can ask Linux Foundation to post on LFX calendar. |
|
@rootfs That sounds good to me. Thank you! |
|
@wangchen615 can you add the zoom meeting ics file? |
- Add Community Meetings section to README - Schedule meetings on first and third Tuesday of each month - First Tuesday: 9-10 AM EST (US EST + Asia Pacific) - Third Tuesday: 1-2 PM EST (US EST + California) - Include Zoom link for easy access Signed-off-by: Chen Wang <[email protected]>
wangchen615
force-pushed
the
add-community-meetings
branch
from
fab4040 to
1f15eac
Compare
- Add separate Zoom links for first and third Tuesday meetings - Include Google Calendar invites for both meeting times - First Tuesday: 9:00-10:00 AM EST with Zoom link and calendar invite - Third Tuesday: 1:00-2:00 PM EST with Zoom link and calendar invite - Fix trailing whitespace in README.md Signed-off-by: Chen Wang <[email protected]>
wangchen615
force-pushed
the
add-community-meetings
branch
from
da91027 to
bd03161
Compare
@rootfs , I updated with google invite link. |
5 participants
PR Description
What type of PR is this?
docs: add tentative bi-weekly community meetings schedule
What this PR does / why we need it:
This PR adds a Community Meetings section to the README.md to establish regular bi-weekly community sync-up sessions. The meetings are scheduled to accommodate contributors across different time zones:
This is a tentative schedule that we will refine based on community feedback. We will collect feedback on this PR and call for proposals for alternative times to better accommodate contributors' availability and preferences.
This will help foster better community engagement, provide regular touchpoints for contributors to stay in sync, and create opportunities for collaboration and feedback sharing across different geographical regions.
Which issue(s) this PR fixes:
Release Notes: No